A source key is a unique identifier that helps you distinguish your applicants coming from different sources and in applying individual rules and settings. For example, you can apply specific verification levels to particular applicants or let applicants be displayed only for the selected accounts.

You can add source keys to any of the following, depending on your scenario:

• Team member roles — to display applicants with the specified source keys.
• Applicant verification levels — to assign levels to applicants coming from the specified sources.
• Webhooks — to be notified about the events occurred for applicants with the specified source keys.
• App tokens — if you want the app token to have access only to a certain group of applicants.
• Transaction monitoring rules — rules will match transactions from specified sources only.

📘

Note

Each Sumsub customer can have up to 300 source keys.

Configure source keys

To configure source keys:

1. In the Dashboard, go to the Source keys page and click Add new source key.
2. Enter a source key name, which can be of any reasonable length and format and consist of letters, numbers, and special characters.
3. Provide an individual support email address for the source key if required, or leave it blank to use your general support email.
4. Save your changes and assign the source key to your applicants as necessary.

🚧

Important

• Once you save the source key, you will not be able to change its name.
• If you delete a source key, you will not be able to search for transactions and applicants holding this key.

Assign source keys to your applicants

To assign a source key:

1. Go to the Applicants page and open an applicant profile.
2. In the Profile Data block, from the Source key from client drop-down list, select a source key and save your changes.

Manage account duplicates for source keys

Configure the system's behavior for handling duplicates associated with particular source keys:

• Allow duplicates — allows creation and verification of applicants with similar names, birthdates, and emails. Use the Max duplicate count field to specify how many duplicate profiles your applicants may have. Example: if you enter 5, applicants can have up to five similar profiles. Any additional profiles (the sixth, seventh, and so on) will be considered duplicates.
• Consider all new similar applicants as duplicates — automatically rejects duplicates of applicant accounts and considers only the first account as a valid one. Example: The applicant gets temporarily rejected by ongoing ID monitoring and instead of uploading a new ID, the applicant creates a new account and then passes verification from scratch. Because of that, the applicant may have two working accounts. In such cases, by having this setting enabled, only the first account will be considered valid.
• Allow different source keys duplicates — allows creation and verification of applicants with similar names, birthdates, phone numbers, and emails, if they come from different sources.
• Forbid duplicates from the key group — forbids creation and verification of applicants with similar names, birthdates, phone numbers, and emails coming from all source keys associated with a specific client.
• Don’t use email for duplicate search — allows creation and verification of the applicants with similar emails.
• Don’t use phone number for duplicate searches — allows creation and verification of the applicants with similar phone numbers.

📘

Note

The duplicate settings for a particular source key override the adjustments set in Global settings→Id Verification. For example, if you allow duplicates globally but forbid them within a particular source key, the system will still check for duplicates across all applicant profiles associated with that source key.